-
Notifications
You must be signed in to change notification settings - Fork 848
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not cache the classify_relation result #4870
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4870 +/- ##
==========================================
- Coverage 90.97% 90.95% -0.03%
==========================================
Files 225 225
Lines 44244 44215 -29
==========================================
- Hits 40252 40215 -37
- Misses 3992 4000 +8
Continue to review full report at Codecov.
|
src/planner/planner.c
Outdated
* If parent reolid is know, the caller can specify it to avoid the costly | ||
* lookup. Otherwise pass InvalidOid. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jnidzwetzki This is the part that should improve planning performance
src/planner/planner.c
Outdated
* If parent reolid is know, the caller can specify it to avoid the costly | ||
* lookup. Otherwise pass InvalidOid. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* If parent reolid is know, the caller can specify it to avoid the costly | |
* lookup. Otherwise pass InvalidOid. | |
* If parent reloid is known, the caller can specify it to avoid the costly | |
* lookup. Otherwise pass InvalidOid. |
It depends on the context, not only on the relation id. The same chunk can be expanded both as a child of hypertable and as an independent table.
It depends on the context, not only on the relation id. The same chunk can be expanded both as a child of hypertable and as an independent table.
Fixes #4708